home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000024_michael@afs.com_Wed Sep 15 08:25 MDT 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
5KB
Received: from yvax2.byu.edu by maine.et.byu.edu; Wed, 15 Sep 93 08:25:31 -0600
Return-Path: <michael@afs.com>
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2YYI4XJXS91X9NY@yvax.byu.edu>; Wed, 15 Sep 1993 08:23:24 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2YYHY7O34934TG2@yvax.byu.edu>; Wed, 15 Sep 1993 08:23:14 MDT
Received: from yvax.byu.edu by alaska.et.byu.edu; Wed, 15 Sep 93 08:24:57 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2YYHHC30W934SR9@yvax.byu.edu>; Wed, 15 Sep 1993 08:22:53 MDT
Received: from uu5.psi.com by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2YYHAJI1C934T8J@yvax.byu.edu>; Wed, 15 Sep 1993 08:22:43 MDT
Received: by uu5.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA06927 for
; Wed, 15 Sep 93 09:50:21 -0400
Received: from escher by afs.com (NX5.67d/3.2.083191-Anderson Financial
Systems) id AA18516; Wed, 15 Sep 93 08:48:12 -0400
Received: by escher (NX5.67d/NeXT-2.0) id AA00450; Wed,
15 Sep 93 08:48:11 -0400
Received: by NeXT.Mailer (1.95)
Received: by NeXT Mailer (1.95)
Date: Wed, 15 Sep 1993 08:48:11 -0400
From: michael@afs.com
Subject: Re: External files & allowable contributions
To: misckit@byu.edu
Reply-To: Michael_Pizolato@afs.com
Message-Id: <9309151248.AA18516@afs.com>
Content-Transfer-Encoding: 7BIT
Status: R
Christopher Kane writes:
>Setting up an analog to /usr/lib/NextStep/Resources, or some
>related analog (/LocalLibrary/*, etc), to achieve some sharing,
>and having Installer (a reasonable method) install the files in
>these sort of locations is a nice idea, if you (as developer) have
>(or Joe User has) the 'power' to write files into these areas.
>Joe User (and developers) on a LAN administered by the organization
>they're part of probably doesn't have write permission into these
>areas. Expecting that sysadmins would be happy to change this,
>or would be accomodating to install things for users, is expecting
>*way* too much. Having your own NeXT on your desk (or being a
>sysadmin) is swell, but there will be a good chunk of users (users
>in education and corporate come to mind) that'd lose on such a
>strategy.
Here's a proposal:
/usr/local/lib/MiscKit/Resources, which parallels
/usr/lib/NextStep/Resources, as the directory for all auxiliary
files associated with the MiscKit library. The installation program
places all the aux files there, and if it happens that it is
implemented at the site as a link to somewhere else, it doesn't
matter. There should be subdirectories if necessary (bundles and
nibs are directories anyway).
If a user is installing the kit in a home directory, then the
directory should be ~/Unix/usr/lib/MiscKit/Resources, same reasons.
>Someone else wrote (sorry, I don't have the original article to
>attribute this):
>>As for the problem of auxiliary files for MiscKit, I'm in favor of
>>something like Don proposed. However, the proper place for bundles
>>is /LocalApps or ~/Apps, not the *Library directories (NeXT says
>>this). Depending on the naming convention for the kit, it would
>>probably be wise to have one bundle per prefix or something.
>
>Does the "bundles belong in *Apps" approach apply to all bundles,
>or just WM inspector bundles or services? I'm skeptical of the
>former (and I can't locate anything that says this), but the later
>two cases are documented.
>
>Preferences bundles have to be in ~/Library/Preferences,
>/LocalLibrary/Preferences, /NextLibrary/Preferences, or
>/NextApps/Preferences.app. If there is a UI-type convention to
>put all bundles in *Apps, NeXT has broken it itself. (Wait a
>minute. What am I saying?! Why do I sound surprised?!! :-))
>But somehow, it just doesn't make sense.
That was my post, and all I can say is that everything I've seen
and heard from NeXT about installing standalone bundles (unless
designated for a special purpose like preferences bundles) says to
put them in /LocalApps or ~/Apps. Note that it is possible to have
a completely general-purpose bundle that is loadable by _any_ app.
Personally, I'm surprised that there are not more of these available;
the possibilities are staggering, especially if bundles' code can
be made shareable like shared libraries. NeXT?
I'm guessing that the reason for putting them in /LocalApps or
~/Apps is that bundles are the same as apps, except they have no
main entry point in the executable. Our "special purpose" is to
centralize all the MiscKit auxiliary files to simplify installation
and maintenance, and that's good enough.
A personal feeling is to watch for bundles (or something very like
them) to become increasingly important in the future, eventually
even replacing apps as the basic unit of execution in NEXTSTEP.
This is based on the direction I've heard NS4.x is headed, as well
as some concepts that I came up with for our internal development
that will prove interesting for the future of apps, at least ours.
Thanx,
Michael
---
Michael_Pizolato@afs.com
NeXTMail appreciated